Skip to content

Conversation

@felipecrs
Copy link
Contributor

Claude Sonnet 4 helped me come up with this solution. It is not perfect, but I think it's better than otherwise.

@CLAassistant
Copy link

CLAassistant commented Jul 14, 2025

CLA assistant check
All committers have signed the CLA.

@felipecrs felipecrs force-pushed the fix-concurrent branch 3 times, most recently from d7fdf12 to a9501c4 Compare July 14, 2025 15:09
@felipecrs
Copy link
Contributor Author

@71 as you reported #9 would you help to test this? I published to NPM at @felipecrs/xz-decompress.

@felipecrs
Copy link
Contributor Author

felipecrs commented Jul 14, 2025

@pimterry performance seems reasonable. It's difficult to compare given it wasn't even working previously.

@71
Copy link

71 commented Jul 15, 2025

@felipecrs Thanks for the fix! This fixed the problem on my end.

@felipecrs felipecrs requested a review from pimterry July 15, 2025 23:03
@pimterry
Copy link
Member

Perfect, thanks! Merged 👍 I'll release as v0.2.3 in just a minute.

@pimterry pimterry merged commit be4ef67 into httptoolkit:main Jul 17, 2025
7 checks passed
@pimterry
Copy link
Member

Oh by the way, in case you're not aware, HTTP Toolkit Pro is free for all contributors to repos in this org - if you're interested just let me know your email (here or via tim @ httptoolkit.com) and I'll set you up with an account.

@felipecrs felipecrs deleted the fix-concurrent branch July 18, 2025 00:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

How to build the project? Concurrent decompression leads to "get_next_output failed with error code 7"

4 participants